InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-02.Z/94-02/text0250.txt

Text File | 1994-02-28 | 21.7 KB | 525 lines

In article <2keraj$[e-mail]>, [e-mail] writes:
|>
|> [e-mail]> writes:
|> > Kevin Brock <[e-mail]> writes:
|> > >This isn't very constructive... Do you have any *specific* comments?
|> > >We can't very well address the issues here if you won't tell us (or
|> > >anyone else) what they are!
|>
|> > >One thing to note is that you're using the 3.11 release.  As you


|> > Telnet
...
|>
|> >     Can't select other than black text on a white background.
|>
|> ..I got yellow on black...

My 3.11 copy happily uses the standard control panel colors,
as you'd expect it to.

-- Martijn
__________
Internet: [e-mail]
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
X-500: c=GB@o=NEXOR Ltd@cn=Martijn Koster
WWW: http://web.nexor.co.uk/mak/mak.html
From [e-mail] Wed Feb 23 11:57:27 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA25533; Wed, 23 Feb 1994 11:57:27 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA22718; Wed, 23 Feb 1994 11:12:22 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 10:52:13
From: [e-mail] (Michael Nuwer)
Message-Id: <[e-mail]>
Organization: Potsdam College
Sender: ses
Subject: Ftp Location for ODIPKT???

I can not seem to find the ODIPKT shim at Oak.Oakland.Edu.  Could someone
please tell me where I might find it.

Thanks

Mike Nuwer
From [e-mail] Wed Feb 23 17:18:07 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA10362; Wed, 23 Feb 1994 12:57:24 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA22336; Wed, 23 Feb 1994 12:27:15 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 23 Feb 1994 17:18:07 GMT
From: [e-mail] (John Lindroth)
Message-Id: <2kg34f$[e-mail]>
Organization: MUSC
Sender: ses
References: <[e-mail]>, <[e-mail]>, <2kbtut$[e-mail]>
Subject: Re: I'm ready to spend money - free and shareware WINSOCK not ok

In article <2kbtut$[e-mail]>, [e-mail] (Karl Denninger) says:
>I am now running another stack, which will remain nameless until I get done
>with my evaluation.    At which point you'll all hear about it.  My first
>impression -- THIS IS WONDERFUL STUFF -- CONSIDER NOTHING ELSE!  It has
>three huge wins - (1) it works, (2) it works, (3) it works.
...
>Best attribute after "it works" of one of these packages:
>        Its affordable.  ~$25 retail.

Karl, please don't hold the silence too long, This sounds great!
BTW, does this stack do Ethernet connections as well? We need both, and at
a price like that, (that works) I can't wait to try it.

John Lindroth
Medical University of SC
Center for Computing and Information Technology
-- I represent only myself --
From [e-mail] Wed Feb 23 17:10:55 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA10374; Wed, 23 Feb 1994 12:57:25 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA22922; Wed, 23 Feb 1994 12:37:36 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 17:10:55 GMT
From: [e-mail] (Sam S. Wong)
Message-Id: <[e-mail]>
Organization: Simon Fraser University, Burnaby, B.C., Canada
Sender: ses
Subject: WinMosaic errors

When I try to run winmosaic, I get the error
"HTAccess:Error accessing"
"http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/NCSAMosaicHome.html".
"Failed DNS Lookup"
I read that I need a NIS to DNS converter or something.  What is this
and where do I get it?
I'm using PC-NFS.

--
# Sam Wong - Ugrad, Computing Science.     #
# SFU Canada.  Email: [e-mail]          #
From [e-mail] Wed Feb 23 16:20:02 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA10386; Wed, 23 Feb 1994 12:57:27 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA17144; Wed, 23 Feb 1994 12:17:50 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 16:20:02 GMT
From: [e-mail] (Morten Lange)
Message-Id: <[e-mail]>
Organization: U.o.Trondheim,Centre for Environment and Development
Sender: ses
References: <[e-mail]>
Subject: Re: Newsgroup not there

In article <[e-mail]> [e-mail] (David A Wolfe) writes:
>Path: ugle.unit.no!trane.uninett.no!news.eunet.no!nuug!news.eunet.fi!news.funet.fi!news.tele.fi!uunet!panix!woof.dialup.access.net!woof
>From: [e-mail] (David A Wolfe)
>Newsgroups: alt.winsock
>Subject: Newsgroup not there
>Date: Tue, 22 Feb 1994 14:42:35
>Organization: PANIX Public Access Internet and Unix, NYC
>Lines: 6
>Message-ID: <[e-mail]>
>NNTP-Posting-Host: woof.dialup.access.net
>X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]


>Sop ther is a newsgroup that appears on my .newsrc for .nn, but
>not that i"m on this nifty trumpet newsreader, I can't seem to find it.

>Any Ideas?
>Thanks

Try to simply edit your news.ini file for Trumpet. It helped me.

Morten
From tcemail!is3.indy.tce.com![e-mail] Wed Feb 23 03:46:00 1994
Received: from relay1.UU.NET by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA11933; Wed, 23 Feb 1994 13:05:42 -0500
Received: from uucp3.uu.net by relay1.UU.NET with SMTP
    (5.61/UUNET-internet-primary) id AAwenc08772; Wed, 23 Feb 94 12:06:25 -0500
Received: from tcemail.UUCP by uucp3.uu.net with UUCP/RMAIL
        ; Wed, 23 Feb 1994 12:06:26 -0500
Reply-To: tcemail![e-mail]
Received: from MSMAIL.INDY.TCE.COM (157.254.98.63) by nipper.indy.tce.com (PMDF
 #12222) id <[e-mail]>; Wed, 23 Feb 1994 11:46 EST
Received: by MSMAIL.INDY.TCE.COM with Microsoft Mail id
 <[e-mail]>; Wed, 23 Feb 94 11:49:26 PST
Date: Wed, 23 Feb 94 11:46:00 PST
From: Fisher Mark <[e-mail]>
Subject: Winsock++?
To: WinSock2 <[e-mail]>
Message-Id: <[e-mail]>
Encoding: 40 TEXT
X-Mailer: Microsoft Mail V3.0


Why, Tom, what are you doing here? (grin)...

To all who have wondered this, here are forwarded messages from Michael J.
Baldwin of GENISYS:
 --------------------------- cut here ---------------------------
On Wed, 6 Oct 93 13:03:03 EDT, "WATCH-OUT WATCH-OUT ABBS IS ABOUT"
<[e-mail]> wrote:
> Does anybody know of any C++ socket classes. I hear there are a few out
there
> but where???

I know that Frontier Technologies and GENISYS both include SOCKET C++
classes in their respective WINSOCK SDK's.
 --------------------------- cut here ---------------------------
!!!!!!!!!!!!! Introducing CWINSOCK !!!!!!!!!!!!
                      - or -
            Classy Winsock for Windows

Thanks to all who have sent me mail with suggestions.

The winsock/packages/cwinsock.zip file at sunsite has my initial cut
at a C++ structure ala MFC.  I would compare it to the CWnd class of
MFC, providing limited functionality.  Its  benefit to most people
will be as a base class.

Please E-mail me your suggestions directly...I will summarize them
later and tranmit them to the list.
 --------------------------- cut here ---------------------------

There is at least 2 more C++ class libraries for sockets, but I believe that
both are for UNIX-style blocking sockets; I know that Douglas Schmidt's
IPC_SAP is for blocking sockets.
======================================================================
Mark Fisher                            Thomson Consumer Electronics
[e-mail]           Indianapolis, IN

"Just as you should not underestimate the bandwidth of a station wagon
traveling 65 mph filled with 8mm tapes, you should not overestimate
the bandwidth of FTP by mail."
From [e-mail] Wed Feb 23 15:30:42 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21644; Wed, 23 Feb 1994 13:57:23 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA27228; Wed, 23 Feb 1994 13:35:57 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 15:30:42 GMT
From: [e-mail] (Lindsey Smith)
Message-Id: <[e-mail]>
Organization: Symantec Corp.
Sender: ses
References: <[e-mail]>
Subject: Re: Winsock++?

In article <[e-mail]> [e-mail] (Thomas R. Bruce) writes:
>Subject: Winsock++?
>From: [e-mail] (Thomas R. Bruce)
>Date: 22 Feb 1994 19:22:11 GMT
>Folks:
>
>This could be -- and probably is -- a FAQ, but has anyone done a C++
>class encapsulating the Winsock API?  I dimly recall spotting
>something which looked like this on sunsite a while back, but don't
>see it now (if it was ever there...)
>
>Best,
>Tb.
>

I'm working on one now. I'm not sure when it'll be available though. My
spare time is quite limited now.

-----------------------------------------------------------------------
Lindsey Smith                                            Symantec Corp.
[e-mail]                                     Baton Rouge, LA
From [e-mail] Wed Feb 23 18:40:04 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21651; Wed, 23 Feb 1994 13:57:25 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA18102; Wed, 23 Feb 1994 13:49:26 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 18:40:04 GMT
From: [e-mail] (Paul J. J. Harrington)
Message-Id: <[e-mail]>
Organization: DSG, Dept. of Computer Science, Trinity College Dublin
Sender: ses
References: <[e-mail]>, <[e-mail]>, <2kbtut$[e-mail]>
Subject: Re: I'm ready to spend money - free and shareware WINSOCK not ok

[ - Karl's posting and others deleted - ]

I am a slip, DOS, and Windows newbie. My first experience with Windows
was to write a C++ socket class for Winsock. It was crap but I learned
a lot.

I tried to set up a slip link under windows for the first time
yesterday and here is my .02 IRP worth: s/w was all from the current
link to the DOS Internet kit from the whats new page in ncsa.

First try was PCTCP 2.2 out of the box. The installation procedure was
awful, the instructions were unclear.

Next, trumpet with internal slip driver. Has ok hooks to edit the
chats, has a pretty nasty chat syntax, could not get it to work
without manually placing a call, logging in and dropping out after
having told the modem to ignore DTR. 560 ms rtt


Next slipdial, no problems with that apart from not reading the line
about x00..sys. Fixed that, chopped away the chat script, logged in,
started the slip driver slip8250.com as provided with slipdial. ran
the PCTCP slipdrv kernel over that and was able to ping, telnet
etc. 800ms rtt which is not too bad considering that I was using a
2400 modem (for various non-technical reasons including children,
brothers and other consumers of electronics)

same with trumpet over the packet driver though the rtt as reported by
ping were about 200ms more that of the DOS FTP ping.

Next, trumpet with internal slip, no compression and some fixed chat
scripts. Great. works very well with around 560ms rtt

Conclusions: I like the slipdial program. It has good scripting, good
diagnostics, good documentation. I like Trumpet because it was very
straightforward to install although the scripting facilities are poor.
It worked well on internal slip and with the packet driver. I _hate_
PCTCP for making a big wolley mammoth of a User guide which is verbose
and frequently unhelpful. I like the quality of the windows apps and I
wish they would all run on a winsock stack. I would like to be able to
get PCTCP working properly under windows.


What is missing:
dial-on-demand:    so that when I click on Eudora, it sets up the link.
        I believe that Distinct offers this? I dislike the
        fact that the link seems to have to be up before
        windows is started?

good scripting ( a lot of the script names are hardwired or require an
        alternative file to be named). slipdial is good,
        comscrpt is bad, trumpet is bad




pjjH




--
Paul Harrington, [e-mail], [e-mail] [phone]
Dept. Computer Sci., Trinity College, University of Dublin, Dublin 2, Ireland.
From [e-mail] Wed Feb 23 15:28:25 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21697; Wed, 23 Feb 1994 13:57:36 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA27227; Wed, 23 Feb 1994 13:35:46 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 15:28:25 GMT
From: [e-mail] (Lindsey Smith)
Message-Id: <[e-mail]>
Organization: Symantec Corp.
Sender: ses
References: <[e-mail]>
Subject: Re: re: WinFSP.... What is it ??

In article <[e-mail]> [e-mail] (Lawrence Levin) writes:

>Subject: re: WinFSP.... What is it ??
>From: [e-mail] (Lawrence Levin)
>Date: Tue, 22 Feb 1994 14:20:13 GMT
>What is WinFSP ?

Lawrence,

This is my canned explanation of what FSP is. WinFSP is (imagine that) a
Windows FSP client. FWIW, there's also a DOS client (which I wrote).

Q1.1: What's alt.comp.fsp?  What's fsp?

        Alt.comp.fsp is a Usenet newsgroup for discussing the FSP file
        transmission protocol.  It was created on Tuesday 4th May 1993
        by Wen-King Su ([e-mail]) after there was no
        objection on alt.config.  Before the newsgroup, there was a
        mailing list (fsp-discussion) for talking about FSP software
        internals.  This newsgroup is for discussion of both writing and
        using the software.

        FSP is a protocol, a bit like FTP (but see below), for moving
        files around.  It's designed for anonymous archives, and has
        protection against server and network overloading.  It doesn't
        use connections, so it can survive things falling over.

        Quote: `FSP is what anonymous FTP *should* be'.


Q1.2: Where can I get FSP from?

        The `official' place for FSP distributions is ftp.germany.eu.net
        (192.76.144.75), in the directory /pub/network/inet/fsp.  It is
        available both by FTP and FSP: the FSP server is on port 2001.
        Another official site is taxus.uib.no (129.177.30.10), which
        only runs an FSP server -- it's on port 9000.  The directory
        on taxus is /fspdist.

        (Note: If you're using Unix, and you don't want to set up a
        server, you might want to get one of the FTP-like clients
        instead -- fspclient, fspcli, or fspsh -- from the same place).

        The latest versions are:

                Unix, VMS:      fsp.271.tar.Z
                OS/2:           fsp2-03b.zip
                MS-DOS:         pcfsp105.zip

        The Unix version is the `original', and was originally written
        by Wen-King Su: Joseph Traub took over for a while, and Phil
        Richards and Pete Bevin maintain it now.  The same distribution
        contains patches by Sven Pechler to make it run on VMS.  Larkin
        Lowrey wrote the OS/2 version, and Lindsey Smith wrote the MS-DOS
        version.  Email addresses are at the end.


Q2.3 Where can I get hold of a list of sites?

        There is a list, maintained by <[e-mail]>,
        which you can get hold of by fsp from ftp.Germany.EU.net (port
        2001):/pub/lists/fsp-servers.  Various other people produce
        lists as well: have a look around!

        You are encouraged to post site information to alt.comp.fsp, and
        if you post in the format below, most people will be able to
        slurp your list straight into their front-end programs.  There's
        an unofficial standard for the format, which you can find on taxus
        in the file "fsplist.std".

Q3.1 What are the main differences between FSP and FTP?  How does FSP work?

        From the user's point of view, the differences are not that
        great, except that some of the more annoying features of FTP
        are gone.  Here are the main differences.

                a. The protocol can stand things going down: if the
                server or the network falls over in the middle of a
                transfer, you can just wait until it comes back up.
                You don't have to reconnect, and even better, if the
                server went down 90% through grabbing a file, you can
                continue from where you left off.

                b. The protocol doesn't need a username or password.
                You just throw packets at the server.  You don't have
                to identify yourself (though you're not completely
                anonymous -- see below).

                c. It's harder to kill off a site with an FSP server
                than with an FTP server.  The FSP daemon is designed to
                be as lightweight as possible:  it doesn't fork off any
                sub-processes, and it takes steps to limit the amount
                of traffic it handles.

                d. The user interface is completely different.  The
                interface that comes with the package consists of
                eleven commands that you can call from the shell.  In
                effect, your shell is providing all the nice functions
                like command line editing.  This makes the interface
                much more versatile than FTP's.  (See below for how to
                get an FTP-like interface, though).

                e. FSP is a bit slower than FTP.  This is a feature,
                not a bug.  The point is to keep the communication
                lightweight, and not to flood the net.

        From the programmer's point of view, fsp is a complete rewrite.

                a. Instead of TCP sockets, it uses datagrams to
                communicate, so that the connection doesn't break on a
                flaky line.

                b. FTP works by opening a port, and then asking the
                server to send a file to it.  FSP uses the same port
                all the time for communication, and asks for segments
                of a file.  So you can start off a transfer half way
                through a file, if you really want to.

                c. The server tries to make sure you don't ask for
                packets too quickly.  Each packet it sends out has a
                random identification number, which the client must
                return on the next request.  (If the client loses the
                number, it must wait a few seconds before the server
                accepts another packet from it).  Therefore, the client
                has to wait for an answer to each request before it
                sends out the next one.



-----------------------------------------------------------------------
Lindsey Smith                                            Symantec Corp.
[e-mail]                                     Baton Rouge, LA
From [e-mail] Wed Feb 23 17:57:44 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA21745; Wed, 23 Feb 1994 13:57:48 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA06584; Wed, 23 Feb 1994 13:13:10 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 23 Feb 1994 17:57:44 GMT
From: [e-mail] (Stewart Johnston)
Message-Id: <[e-mail]>
Organization: HookUp Communication Corporation, Waterloo, Ontario, CANADA
Sender: ses
Subject: Looking for simple Winsock examples

Looking for simple Winsock examples

Looking for a simple C source code example of how to use the winsock.dll  .
I've looked through all the FAQs and can not find any info on simple winsock examples.

I have two computers side by side and I would like to connect them with
a SLIP running winsock TCP/IP.  But first I have to learn how to use the
winsock DLL.

I already have winsock.dll and winsock.h .  Do I need anything for the slip?

Could Someone Please Point me in the right direction.
Thanks
Stewart Johnston
[e-mail]
From [e-mail] Wed Feb 23 18:44:08 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA02499; Wed, 23 Feb 1994 14:57:26 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA14908; Wed, 23 Feb 1994 14:33:27 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 23 Feb 94 18:44:08 GMT
From: [e-mail] (Neil Mccurdy)
Message-Id: <[e-mail]>
Sender: ses
Subject: Agonizing transmission speeds w/ HGopher

Hi --

I haven't heard anyone comment on this... is gopher notoriously slow
or do I have it set up wrong?  We're talking on the order of 8
minutes for a 500k file using ethernet!  Could this be a result of
the trumpet winsock stack problem that everyone has been talking
about?

Neil